Adaptable radio link for wireless communication networks

ABSTRACT

A system for transmitting wireless messages from a Wireless Access Internet Network architecture for providing users a plurality of wireless protocols to access a communications network. The architecture comprises a wireless client for providing an authentication message. The wireless client includes a radio link adaptation layer and a radio interface, and the radio link adaptation layer adapts to a plurality of wireless protocols. The architecture further includes a wireless server in communication with the wireless client. The wireless server includes a charging module, a Home Location Register (HLR) signaling module, a Domain Naming System (DNS)/Dynamic Host Configuration Protocol (DHCP) Remote Authentication Dial-in User Service (RADIUS) module, a radio link adaptation layer, and a radio access point in communication with the radio interface. Additionally, the architecture includes a data network in communication with the wireless server.

RELATED APPLICATION

The present application claims the benefit of U.S. ProvisionalApplication No. 60/384,623, filed on May 31, 2002.

BACKGROUND OF THE INVENTION

The present disclosure relates generally to a communications system and,more particularly, to a method and apparatus for an adaptive radio linkfor a wireless communication network.

There exists several wireless standard protocols for use incommunications networks. However, no efficient method or system existsfor computing devices to access those communications networks whilehaving the choice of using more than one standard wireless protocol. Forexample, IEEE 802.11 devices can not use GPRS devices.

Therefore, what is needed, is a system and method for a computing deviceto access a wireless network through at least two wireless standardprotocols.

SUMMARY OF THE INVENTION

The present disclosure provides a system and method for providecomputing devices access to a wireless network through the use of atleast two wireless standard protocols.

Therefore, in accordance with the previous summary, objects, featuresand advantages of the present disclosure will become apparent to oneskilled in the art from the subsequent description and the appendedclaims taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a GPRS network architecture;

FIG. 2 illustrates the Wireless Access Internet Node (WAIN) systemutilizing the 802.11 radio transport;

FIG. 3 shows details of the system elements of the WAIN client, the WAINserver and the SS7 gateway of the WAIN system;

FIG. 4 illustrates the WAIN system connected to the UMTS core network;

FIG. 5 illustrates the WAIN server integrated with a 3G RNC;

FIG. 6 illustrates the WAIN system connected to a cdma2000 network;

FIG. 7 illustrates GPRS networks with a roaming arrangement;

FIG. 8 illustrates a WAIN system supporting roaming users in GPRS/3Gnetworks;

FIG. 9 illustrates the WAIN system connected to the SS7 network througha SS7 Gateway;

FIG. 10 illustrates the WAIN system with a subscription/authenticationdatabase HLR′/AuC′ with an IP interface;

FIG. 11 illustrates how the WAIN signaling protocol is simplified;

FIG. 12 illustrates GPRS data protocol migration from 2.5G to 3G;

FIG. 13 illustrates GPRS control protocol migration from 2.5G to 3G;

FIG. 14 compares the SGSN/HLR/SMS-GW interface to the WAINserver/HLR/SMS-GW interface via the SS7 Gateway;

FIG. 15 focuses on how the GPRS/3G protocols are adapted to the PacketRadio Subsystem in the WAIN architecture;

FIG. 16 illustrates GPRS data and signaling protocols for an integrated2.5G/WAIN server over 802.11;

FIG. 17 illustrates 3G data and signaling protocols for an integratedRNC/3G/WAIN server;

FIG. 18 illustrates how the GPRS user data transfer is simplifiedutilizing the WAIN system;

FIG. 19 illustrates how the GPRS data protocols are integrated with theWLAN protocols in the WAIN system;

FIG. 20 illustrates how a WAIN server could connect to a home GGSN in amobile network; and

FIG. 21 focuses on the interface between the WAIN server and the CGF inthe mobile network.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The present disclosure can be described by the embodiments given below.It is understood, however, that the embodiments below are notnecessarily limitations to the present disclosure, but are used todescribe a typical implementation of the invention. A list ofdefinitions and abbreviations will first be described and then thedetails of the embodiment will be described.

Definitions and Abbreviations 2G Second generation; generic name forsecond generation of digital mobile networks (such as GSM) 2.5G 2Gmobile system enhanced with higher data rates and generally includingpacket radio transmission and switching such as GPRS 3G Thirdgeneration; generic name for next-generation mobile networks (UTMS,cdma2000; sometimes GPRS with an enanced radio system is also called 3Gin North America) AAA Authentication, Authorization, and Accounting AuCAuthentication Center BG Border Gateway BGP Border Gateway Protocol BSCBase Station Controller BSS Base Station System BTS Base TransceiverStation CDMA Code Division Multiple Access; wireless access protocol CDRCall Detail Record CGF Charging Gateway Functionality EIR EquipmentIdentity Register ESP Enhanced Security Protocol ETSI EuropeanTelecommunications Standards Institute Gb Interface between a SGSN and aBSS Gc Interface between a GGSN and a HLR Gd Interface between aSMS-Gateway and a SGSN, and between a SMS-IWMSC and a SGSN Gf Interfacebetween a SGSN and an EIR GGSN Gateway GPRS Support Node Gi Referencepoint between a GPRS and an extemal packet data network Gn Interfacebetween two GSNs within the same PLMN (a GSN can be a SGSN or a GGSN) GpInterface between two GSNs in different PLMNs GPRS General Packet RadioService Gr Interface between a SGSN and a HLR Gs Interface between aGGSN and a MSCIVLR GSM Global System for Mobile communications; wirelessstandard GW Gateway HDLC High-level Data Link Control HLR Home LocationRegister IMSI International Mobile Subscriber Identity IP InternetProtocol ISP Internet Service Provider IWMSC Inter Working MobileSwitching Center LLC Logical Link Control MAC Medium Access Control MMMobility Management MS Mobile Station MSC Mobile Services SwitchingCenter MT Mobile Terminal PDA Personal Digital Assistant PDN Packet DataNetwork PDP Packet Data Protocol PLMN Public Land Mobile Network PSTNPublic Switched Telephone Network QoS Quality of Service RADIUS RemoteAuthentication Dial-in User Service RNC Radio Network Controller (3G)SGSN Serving GPRS Support Node SIM Subscriber Identity Module SMS ShortMessage Service SMSC Short Message Service Center; also known as SMS-Cand SM-SC SS7 Signaling System Number 7 SMSC Short Message ServiceCenter TDMA Time-division Multiple Access Protocol; wireless protocol UmRadio interface between the MS and the CPRS network UMTS UniversalMobile Telecommunications System VLR Visitor Location Register VPNVirtual Private Network WMN Wireless Access Internet Node WISP WirelessInternet Service Provider WC WAIN Client WS WAIN Server

Now turning to FIG. 1 a General Packet Radio Service (GPRS) based mobiledata network architecture is shown. GPRS is a new enhancement to GSMcommunications for supporting packet data transfer over a mobilenetwork. GPRS is the basis for packet data service in a 3^(rd)Generation (3G) mobile standard called Universal MobileTelecommunications System (UMTS). UMTS is one of the major new 3G mobilecommunications systems being developed within the framework which hasbeen defined by the ITU and known as IMT-2000. The subject of intenseworldwide efforts on research and development throughout the presentdecade, UMTS has the support of many major telecommunications operatorsand manufacturers because it represents a unique opportunity to create amass market for highly personalized and user-friendly mobile access totomorrow's “Information Society.”

UMTS delivers pictures, graphics, video communications and otherwide-band information as well as voice and data, directed to people whomay be on the move. UMTS builds on and extends the capability of mobiletechnologies (like digital cellular and cordless) by providing increasedcapacity, data capability and a far greater range of services using aninnovative radio access scheme and an enhanced, evolving core network.The packet domain of UMTS is based on GPRS. Some characteristics of GPRSinclude: a data rate up to 150+ kbps (on entire radio channel, 8 timeslots); “always connected”-session active even without radio resourceassigned; error detection and correction for reliability; securityfunctions to protect mobile's identity and packet data transfer; roamingthrough a secure tunneling (over IP network); standardized EP protocols;and volume based charging.

The Base Station Systems (BSSs) 100, 102 are responsible for radiotransmission, radio source management and access control. The BSSs 100,102 include, Base Transceiver Station (BTS) 104, 106, 108 and BaseStation Controllers (BSC) 110, 112. The BSSs 100,102 serve the MobileStations (MSs) 114, 116, 118, 120 in their coverage area via a radiolink 122.

One or more mobile BSSs 100, 102 are connected to a Serving GPRS SupportNode (SGSN) 124 which performs packet switching and mobility managementfunctions. Some SGSN functions include: Frame Relay based Gb interfaceto BS; GPRS attach, authentication, routing area updating, paging;coordination between GPRS and CS via Gs interface; PDP contextactivation/deactivation; encryption and error protection (LLC);compression and segmentation; Short Message Services (SMS) Control/Relayfunctions and Gd interface; GTP tunneling over Gn/Gp interface; Grinterface to HLR; and charging data collection (S-CDR, M-CDR, SMS-CDRs)and Ga interface to CGF.

The SGSN 124 also detects MSs 114, 116, 118, 120 in the local area forthe transmission and receipt of packets. Additionally, the SGSN 124locates and identifies the status of MSs 114, 116, 118, 120 and gatherscrucial call information, which is an essential aspect of billing.Accordingly, the SGSN 124 is connected to the Charge Gateway Function(CGF) 128, which in turn is connected to the Billing System 130. Inaddition to providing mobility management and connectivity between theBSSs 100, 102 and the Gateway GPRS Serving Node 126, other key SGSN 124functions include ciphering, compression and interaction with GSMcircuit switched services for mobile paging and SMS. The SGSN 124 inthis embodiment is connected to the Short Message Service Center (SM-SC)132 through the SMS Gateway 134.

One or more SGSNs 124 can be connected to a GGSN 126 for interworkingwith external IP Network (also known as PDN for Packet Data Network)136. The GGSN 126 acts as a gateway between GSM networks and public IPnetworks. Some of the GGSN functions include: a Gn Interface (similar toSGSN's); Packet Data Routing and Relay; PDP context activation anddeactivation; address translation and mapping; packet store/forward andsequencing; Gi Interface; IP interworking including transparent IPaccess and non-transparent IP access requiring authentication;interworking for other PDP types (PPP, OSP); Gc interface to HLR; andcharging data collection (G-CDR) and Ga interface to CGF.

The GGSN 126 can connect directly to the Internet using IP over avariety of physical and tunneling protocols. The GGSN 126 can alsofunction as a fire wall, to ensure that all incoming and outgoing datais authorized adding security to an enterprise network. In addition toproviding GSM connectivity to external data networks such as theInternet, the GGSN 126 includes all standard based functionality andeven more with authentication, encryption, routing, firewall filtering,bandwidth and system management.

Moreover, there is a database called Home Location Register (HLR) 138connected to the SGSN 124 and GGSN 126 that stores subscription data forall mobile users that are subscribed in any particular home network 140.Further, an MS's security information is stored in an AuthenticationCenter (AuC) 138 (depicted as the same entity as the HLR in this figure)which communicates with the SGSN 124 via the HLR 138 for authenticationpurposes.

In the GSM/GPRS architecture, a MS 114 consists of a Mobile Terminal(MT) 140 and a Subscriber Identity Module (SIM) 142 (both MT and SIM areshown as the same entity as MS in this figure). The MT 140 supports theradio interface communicating with the BSS 100 and the SIM 142 cardstores a subscriber's subscription and security information (there isalso a Universal Subscriber Identity Module defined in the UMTSstandard).

The SIM 142, the MT 140, the SGSN 124 and the AuC 138 are the onlyentities involved in the security procedure in this embodiment. Inparticular, the SIM 142 in MS 114 and the AuC 138 are the twoauthenticating entities where a unique authentication key (Ki) is storedfor each mobile subscriber. The authentication information is exchangedbetween the MT 140 and SGSN 124. However, the SIM 142 is the key to thepersonalized service, security and billing. Before a MS 114 can use anyGPRS services, it must attach itself to the network 140 through a GPRSAttach procedure, as dictated within the GPRS standard. More details arediscussed in co-pending U.S. patent application Ser. No. 10/200,994which is incorporated by reference above.

Now referring to the rest of the GPRS architecture depicted, the SGSN124 is also shown connected to another SGSN 144 and Border Gateway 146.The BG 146 in turn connects this network 140 to another Public LandMobile Network (PLMN) 148 with its own BG 150, a BSS 152, another SGSN154 and a GGSN 156, along with its MS 158. The BG 150 provides securityfor communication between two networks.

The SGSN 124 is also connected to an Equipment Identity Register (EIR)162 and a MSC/VLR 162, which in turn is connected to the Public SwitchedTelephone Network (PSTN) 164.

Now turning to FIG. 2, the Wireless Access Internet Node (WAIN)technology of the invention is shown. The WAIN system integrates theGPRS network and security functionality with an independent high speedradio system such as IEEE 802.11. The WAIN system consists of a WAINClient (WC) 200 and a WAIN Server (WS) 204 in the network. The WAINsupports wireless Internet access and data transfer at a high speedwhile providing connectivity to the mobile network for mobility,security and billing services. The WC 200 supports high layer GPRSterminal functions, interfaces to the SIM card and adapts to theunderlying radio system 206, which in this case is 802.11.

The WS 204 supports the GPRS network functions of the SGSN, and the GGSNand interfaces to a HLR/AuC 208 through a SS7 Gateway 210. The WS alsoconnects through the IP network 212 to the 802.11 Access Point (AP) 214,that in turn communicates with the 802.11 Station (STA) module 206 inthe WC 200. By combining the multiple network elements into one singlenode, all unnecessary intermediate interfaces and protocols are removedin the WS 204. Therefore, the system architecture can be greatlysimplified and cost can be significantly reduced compared to theconventional mobile network architecture. More detail about the WAINtechnology can be found in co-pending U.S. application Ser. No.09/851,681, which is commonly assigned. In addition, a radio linkadaptation module in both the WC 200 and the WS 204 allows the WAINarchitecture to support multiple radio technologies. More details followon the methodology implemented to support multiple radio technologies.

In addition to the HLR/Auc 208 node, the SS7 gateway 210 also connectsthe WS 204 to a SMS-Gateway (SMS-GW) 216 within the GPRS/3G network 218shown. The GPRS/3G network also shows a CGF 220 and a GGSN 222 thatconnect to the WS 204 through the IP network 212.

Now turning to FIG. 3, the system elements of the WC 300 and the WS 302are shown as they are adapted to communicate over the 802.11 radiotransport. In addition, the system elements of the SS7 Gateway 304 arealso shown, along with the connections between IP network 306 and the WS302 and the SS7 Gateway 304.

The peer system elements in the WC 300 and the WS 302 include: systemcontrollers 308, 310; registration modules 312, 314; IP Relay modules316, 318; SM modules 320, 322; GMM modules 324, 326; SNDCP modules 328,330; LLC modules 332, 334; and Radio Link Adaptation modules 336, 338,respectively. In addition, the WC 300 also contains an applicationslayer 340 and an applications GUI 342, a Comm WSAP (WAIN Service AccessPoint) 344, a SIM interface 346 connected to a SIM card 348, and a802.11 station module 350.

The WS 302 also contains an Operation and Maintenance (O&M) module 352,a charging module (for billing) 354, a HLR signaling module 356, aDNS/DHCP RADIUS module 360, and an 802.11 AP 362.

The peer modules between the WS 302 and the SS7 Gateway 304 include:GTP/E-GTP modules 364, 366; TCP/UDP and TCP modules 368, 370; andIP/L2/L1 modules 372, 374. The SS7 Gateway also includes a E-GTP to MAPInterworking module 376, a MAP module 378, a TCAP/SCCP module 380, and aMTP/L2/L1 module 382. The WS 302 connects to the SS7 Gateway 304 whichin turn connects to the SS7 network and specifically to any HLR/AuC thatis needed for authentication purposes. Additionally, the IP network 306is connected to the other WAIN servers, GGSNs, or CGFs 386.

Now turning to FIG. 4, the WAIN system is depicted connected to the UMTScore network. In this embodiment, two MSs 400, 402 are connected to twoNode Bs 404, 406, and in turn connected to a RNC 408 which is connectedto a 3G-SGSN 410. In addition, the 802.11 WLAN 412, which includes twoWAIN Clients 414, 416, connected to two APs 418, 420, and connects tothe WAIN server (WS) 422. In turn, the WS 422 connects to the RADIUSserver 424 for User ID/Password authentication, and the Intra-PLMN IPBackbone 426 to connect to the data network and the CGF/Billing server428. Moreover, the WS 422 connects to the HLR/AuC 432 and the SMS-GW 434through the SS7 Gateway 436 and the SS7 Network 430. Also depicted inthis figure, is a GGSN 438 and the public Internet 440.

Now turning to FIG. 5, a WAIN server is shown integrated with a 3G RNC.Although most elements are similar to FIG. 4, the WS is shown integratedwith a 3G RNC and depicted as WS/3G RNC 500. Additionally, as an exampleof the adaptability of the WAIN architecture to different radiotechnologies, a MS 502 is shown connected to a Node B 504 which in turnis connected to the combined WS/3G RNC 500.

FIG. 6 depicts another possible radio implementation. Here, the WAINsystem is shown connected to a cdma2000 network. This embodimentincludes two MTs 600, 602 connected to two BTS 604, 606, and in turnconnected to a BSC 608 which is connected to a MSC/VLR 610 and a privateEP backbone 626. In addition, the 802.11 WLAN 612, which includes twowireless SIM users 614, 616, connected to two APs 618, 620, and connectsto the WAIN server (WS) 622. In turn, the WS 622 connects to the AAAserver 624 for authentication, the HA (Home Agent) 630 and the PDSN/FA(Foreign Agent) 628 through the Private IP Backbone 626. Moreover, theMSC/VLR 610 connects through the SS7 Network 632 to the HLR/AuC 634.Also depicted in the this figure, is the public Internet 636 connectedto the WS 622 through the private IP backbone 626.

Now turning to FIG. 7, two GPRS networks with a roaming arrangement aredepicted. Operator A's network 700 includes MSs 702, 704 connected tothe a BSS 706 and SGSN 708. Moreover, a SMS-GW 710, a GGSN 712, aHLR/AuC 714 and a CGF/Billing server 716 are connected to the SGSN 708,as well as BG 718. The GGSN 712 is connected to a VPN 720 and the publicInternet 722.

In turn the BG 718 connects to Operator B's network 724 through aRoaming exchange network 726 to Operator B's BG 728. In addition,Operator B's network 724 also includes MTs 730, 732 connected to the aBSS 734 and SGSN 736. Moreover, a SMS-GW 738, a GGSN 740, a HLR/AuC 742and a CGF/Billing server 744 are connected to the SGSN 736. The GGSN 740is also connected to the public Internet 722.

Now turning to FIG. 8, a WAIN system supporting roaming users in GPRS/3Gnetworks is shown. Within one WLAN 800, two WCs 802, 804 are shownconnected to two Access Points 806, 808 which are connected to WS 810.Another WLAN 812 is shown with one WC 814 and one Access Point 816connected to another WS 818. The WSs 810, 818 are in turn connected tothe public Internet 826 and the HLR/AuC 836 and SMS-GW 834 through theSS7 Gateway 824 and the SS7 Network 838. In addition, the WSs 810, 818are also connected to a RADIUS server 820 for non-SIM authenticationpurposes, an O&M Control Station 822, a CGF/Billing server 828 and aGGSN 830, both within a GPRS/3G network 832. However, the WAIN Systemcan connect to multiple GPRS/3G networks.

In this embodiment, authentication can be accomplished in one of twomethods. One method is utilizing the RADIUS server for non-SIM users.However, this method can sometimes be costly and difficult to manage.Another method is to transport the SIM information to the WAIN servers818, 810 which forward to the HLR/AuC 836 through the SS7 gateway 824 toobtain authentication information for authenticating the client.

Now turning to FIG. 9, the WAIN system is shown connected to the SS7network through a SS7 Gateway. Within one WLAN 900, two WCs 902, 904 areshown connected to two APs 906, 908 which are connected to WS 910.Another WLAN 912 is shown with two WCs 914, 916 and two APs 918, 920connected to another WS 922. The WSs 910, 922 are in turn connected tothe public Internet 924. Moreover, the WSs 910, 922 also connect to thea HLR/AuC 926 through a SS7 Gateway 928 and the SS7 Network 930.

Now turning to FIG. 10, the WAIN system is shown with asubscription/authentication database HLR′/AuC′ with an IP interface.Within one WLAN 1000, two WCs 1002, 1004 are shown connected to two APs1006, 1008 which are connected to WS 1010. Another WLAN 1012 is shownwith two WCs 1014, 1016 and two APs 1018, 1020 connected to another WS1022. The WSs 1010, 1022 are in turn connected to the public Internet1024. However, unlike FIG. 9, this figure connects the WSs 1010, 1022 tothe HLR′/AuC′ 1026 without the use of a SS7 Gateway or a SS7 Network.

Now turning to FIG. 11, the WAIN signaling protocol is shown. Instead ofthe having the GB-L1 layer 1100, the network service layer 1102 and theBSSGP layer 1104 in the SGSN and the BSS in a conventional GPRS system,the WAIN server eliminates them and lays just the SM/GMM layer 1106 andthe LLC layer 1108 on top of the RLC layer 1110, the MAC layer 1112 andthe Um-L1 layer 1114. In turn the RLC layer 1110, the MAC layer 1112 andthe Um-L1 layer 1114 communicate directly with the corresponding layers1116, 1118, 1120 in the MS 1122. The RLC, MAC and Um-L1 can be replacedby the 802.11 protocol layers.

Now turning to FIG. 12, data protocol migration from 2.5G to 3G isdepicted. When the WAIN server replaces the conventional 2.5GBSS/SGSN/GGSN, the BSSGP 1200, the Network Service 1202, and the Gb-L11204 layers are eliminated in the BSS 1206 and the SGSN 1208.Additionally, the GTP 1210, the UDP 1212, the IP 1214, the L2 1216 andthe Gn-L1 1218 layers are also eliminated from the SGSN 1208 and theGGSN 1220. The simplified 2.5G WAIN server 1238 thus includes the IPRelay layer 1222, the SNDCP layer 1224, the LLC layer 1226, the RLClayer 1228, the MAC layer 1230, the Um-L1 layer 1232, the L2 layer 1234and the Gi-L1 layer 1236.

Moreover, since the 3G WAIN server eliminates the GTP-U 1240, the UDP/IP1242, the AAL5 1244 and the ATM 1246 layers are eliminated in the RNS1248 and the SGSN 1250. Additionally, the GTP-U 1252, the UDP/IP 1254,the L2 1256 and the Gn-L1 1258 layers are also eliminated from the SGSN1250 and the GGSN 1260. The simplified 3G WAIN server 1262 thereforeincludes the IP Relay layer 1264, the PDCP layer 1266, the RLC layer1228, the MAC layer 1270, the Uu-L1 layer 1272, the L2 layer 1274 andthe Gi-L1 layer 1276. In sum, the intermediate interfaces are eliminate;Frame Relay and ATM are eliminated in the WAIN server; the PDCP layer issimilar to the SNDCP layer; the LLC and the RLC are combined in the 3Gserver; and the major differences are in the MAC and U-L1 layers, butthey can also be replaced by 802.11.

Now turning to FIG. 13, control protocol migration from 2.5G to 3G isdepicted. When the WAIN server replaces the conventional 2.5GBSS/SGSN/GGSN, the BSSGP 1300, the Network Service 1302, and the Gb-L11304 layers are eliminated in the BSS 1306 and the SGSN 1308. Thesimplified 2.5G WAIN server 1310 thus includes the SM/GMM/SMS layer1312, the RRM/LLC layer 1314, the RLC layer 1316, the MAC layer 1318,and the Um-L1 layer 1320.

Furthermore, since the 3G WAIN server eliminates the RANAP 1322, theSCCP 1324, the Signaling Bearer 1326, the AAL5 1328 and the ATM 1340layers are eliminated in the RNS 1342 and the SGSN 1344. The simplified3G WAIN server 1346 therefore includes the SM/GMM/SMS layer 1348, theRRC layer 1350, the RLC layer 1352, the MAC layer 1354, and the Uu-L1layer 1356. In sum, the Gb/Iu interfaces are eliminated; there is noFrame Relay and ATM in the WAIN server; the SM/GMM/SMS layers aresimilar; and the major differences are the MAC and U-L1 layers, but canbe replaced by 802.11.

Now turning to FIG. 14 the SGSN/HLR/SMS-GW interface is compared to theWAIN Server/HLR/SMS-GW interface via the SS7 Gateway. In a conventionalGPRS architecture, the SS7 layers of an SGSN 1400 communicate directlyto the peer layers of HLR or SMS-GW 1402. However, in the WAINarchitecture, the SS7 gateway 1404 maps the IP based layers of the WAINserver 1406 to the SS7 layers of HLR or SMS-GW 1402.

In sum, the WAIN system centralizes the SS7 stack in the SS7 gateway1404 which performs E-GTP/IP to MAP/SS7 conversion for the Gr and Gdinterfaces. Accordingly, this conversion makes all network interfaces IPbased. Therefore, the overall signaling architecture is greatlysimplified and becomes very cost effective.

FIG. 15 shows how the GPRS/3G protocols are conceptionally adapted tothe Packet Radio Subsystem in the WAIN architecture. As depicted, theSIM module 1500 communicates directly with the GPRS/3G protocols 1502 inthe WAIN client 1504. In turn those protocols 1502 are directly linkedto the Radio Link adaptation layer 1506 and then to the Radio Subsystem1508. In turn, the Radio Subsystem 1508 of the WAIN client 1504communicates directly to the Radio Subsystem 1510 of the WAIN server1512, which in turn is linked to the its respective Radio Linkadaptation layer 1514 and its protocols 1516. The division of the RadioLink adaptation layer and the Radio Subsystem allow the WAIN systemarchitecture to accommodate multiple radio protocols.

Although 802.11 is used in most of the embodiments, as this figureillustrates, the radio subsystem is also adaptable to a BlueTooth, 3G orGPRS implemtation. Similarly, the radio subsytem is also adaptable tomany more wireless protocols including 802.15 and HIPERLAN. However, ifthe user is not using an existing wireless account that can be checkedthrough the HLR, the user's credentials can be authorized through theRADIUS server.

The WAIN server protocols 1516 connect the WAIN server to the EPnetwork, which in turn is connected directly to the CGF 1520 and anyGGSNs 1522 in the GPRS/3G network 1524. Also, through the SS7 gateway1526, the IP network is connected to the SMS-GW 1528, and the HLR/AuC1530. Such an architecture allows packet radio (e.g. 802.11) to providehigh-speed and low-cost radio communication. In addition, the GPRS/3Gstandard interfaces and protocols enable mobility, security and billing.Moreover, the GSM SIM card provides convenient subscriber data forauthentication and billing.

FIG. 16 shows yet another example of the WAIN architectures flexibilityto accommodate different radio technologies, data and signalingprotocols for an integrated 2.5G/WAIN server over 802.11 are shown. Incomparison with FIG. 3, the WAIN client in this figure includes similarmodules, but the 802.11 AP 362 in this figure is detailed as a 802.11module 1600 that communicates to a 802.3 module 1602 that connects theAP 362 through a wired LAN to the 802.3 module 1604 in the WAIN server302. Again, the adaptablility of the radio link adaptation layer and theradio subsystem allows many other possible wireless protocol schemes toconnect the WAIN client to the WAIN server.

Now turning to FIG. 17, data and signaling protocols for a 3G-WAINServer are shown. The elements of the 3G-WAIN Server 1700 include thePDCP, the RLC, the MAC and the Uu-L1 layers 1702, the SM/GMM/SMS, the IPRelay, the GTP/GTP′/E-GTP, the TCP/UDP, the IP, the L2 and L1 forGp/GA/Gr/Gd, the L2 and L1 for Gi, the O&M, the Charging and the HLRSignaling modules 1704. In addition, the 3G-MS or 3G-WAIN clientfunctions 1706 are also shown. Moreover, the MAC and L1 layers 1708 canbe replaced by the 802.11 radio protocol.

Now turning to FIG. 18, how the GPRS user data transfer is simplifiedutilizing the WAIN system is shown. As indicted by the figure, the BSSGP1800, the Network service 1802, and the Gb-L1 1804 layers are eliminatedfrom the BSS 1806 and the SGSN 1808, as well as the GTP 1810, the UDP1812, the IP 1814, the L2 1816, and Gn-L1 1818 layers are eliminatedfrom the SGSN 1808 and the GGSN 1820. In addition, the RLC 1822, the MAC1824, and Um-L1 layers in the MS 1826 and the BSS 1806 can be replacedin this figure with 802.11.

Now turning to FIG. 19, how the GPRS data protocols are integrated withthe WLAN protocols in the WAIN system is shown. In comparison with FIG.3, the WAIN client in this figure includes similar modules, but the802.11 AP 362 in this is detailed as a 802.11 module 1900 thatcommunicates to a 802.3 module 1902 that connects the AP 362 through awired LAN to the 802.3 module 1904 in the WAIN server 302.

Now turning to FIG. 20, how a WAIN server could connect to a home GGSNin a mobile network is shown. Similar to FIGS. 3 and 19, this figureshows how the protocol layers communicate between the WAIN client 300and the WAIN server 302. However, this figure also shows the protocollayer communications from the WAIN server 302 and a Home GGSN 2000.Reciprocal layers to the WAIN server 302 in the GGSN include: the Gp-L12002, the L2 2004, the IP 2006, the UDP 2008, the GTP 2010, the IP Relay2012, the L2 2014, and the Gi-L1 2016 layers.

Now turning to FIG. 21, the interface between the WAIN server and theCGF in the mobile network is described. The WAIN server 2100 and the CGF2102 in the mobile network both contain GTP layers 2104, the TCP/UDPlayers 2106, the IP layers 2108, the L2 layers 2110, and the L1 layers2112. All Call Detail Records (CDRs) from the WAIN server aretransmitted to the CGF through this interface.

It is understood that several modifications, changes and substitutionsare intended in the foregoing disclosure and in some instances somefeatures of the invention will be employed without a corresponding useof other features. Accordingly, it is appropriate that the appendedclaims be construed broadly and in a manner consistent with the scope ofthe invention.

What is claimed is:
 1. A Wireless Access Internet Network architecturefor providing users a plurality of wireless protocols to access acommunications network, the architecture comprising: a wireless clientwherein the wireless client provides an authentication message andincludes: a first radio link adaptation layer and a radio interface,wherein the first radio adaptation layer adapts the authenticationmessage to a plurality of wireless protocols; a wireless server incommunication with the wireless client wherein the wireless serverincludes: a charging module; a Home Location Register (HLR) signalingmodule; a Domain Naming System (DNS)/Dynamic Host Configuration Protocol(DHCP) Remote Authentication Dial-in User Service (RADIUS) module; asecond radio link adaptation layer and a radio access point incommunication with the radio interface; a data network in communicationwith the wireless server, wherein the authentication message istransmitted through the first radio link adaptation layer and the radiointerface, then through the radio access point and the second radio linkadaptation layer; and wherein the wireless server communicates theauthentication message to the data network.
 2. The architecture of claim1 further including a second wireless client in communication with thewireless server.
 3. The architecture of claim 1 further including: awireless mobile device with a cellular protocol; and a base stationsystem (BSS) in communication with the wireless mobile device andconnected to the data network wherein the wireless server can transmitmessages from the wireless client to the wireless mobile device throughthe data network and the BSS.
 4. The architecture of claim 1 furtherincluding: a wireless mobile device with a wireless protocol; areceiving system in communication with the wireless mobile device; aSGSN in communication with the receiving system and connected to thedata network wherein the wireless server can transmit messages from thewireless client to the wireless mobile device through the data network,the SGSN and the receiving system.
 5. The architecture of claim 1further including a charge and billing gateway device in communicationwith the wireless server wherein the wireless server transmits chargeand billing information to the gateway device.
 6. The architecture ofclaim 1 further including a RADIUS server connected to the wirelessserver wherein the authentication message includes a User ID and apassword and wherein the wireless server transmits the User ID andpassword to the RADIUS server and the wireless server receives anappropriate approve/deny message back from the RADIUS server.
 7. Thearchitecture of claim 1 further including a RADIUS server connected tothe wireless server wherein the wireless server transmits accountingdata to the RADIUS server.
 8. The architecture of claim 1 furtherincluding a HLR connected to the wireless server wherein the wirelessserver transmits an authentication information request message to theHLR and receives requested authentication data back from the HLR.
 9. Thearchitecture of claim 1 further including: an AuC connected to thewireless server wherein the wireless server transmits the authenticationmessage to the AuC and receives an appropriate approve/deny message backfrom the AuC; and a GPRS Gateway Support Node (GGSN) in communicationwith the wireless server; a virtual private network (VPN) incommunication with the GGSN, wherein the wireless client is allowedaccesss to the VPN through the GGSN.
 10. The architecture of claim 1further comprising: an identity module connected to the wireless clientand having a unique authentication key, wherein the authenticationmessage includes information about the authentication key.
 11. Thearchitecture of claim 10 further comprising: an AuC connected to thewireless server, wherein the wireless server transmits theauthentication message to the AuC and receives from the AuC a messageindicating the authenticity/inauthenticity of the information about theauthentication key.
 12. The architecture of claim 1 wherein the packetdata network is an internet protocol network.
 13. The architecture ofclaim 1 wherein each of the first and second wireless servers includesmeans for converting the authentication message to a format acceptablefor authentication by an authenticating node in a UMTS network.
 14. Thearchitecture of claim 1 wherein each of the first and second wirelessclients include a subscriber interface module (SIM) for providing theauthentication message to the respective WLAN.
 15. The architecture ofclaim 1 further including a charge and billing gateway device incommunication with the wireless servers wherein each of the wirelessservers transmits charge and billing information to the gateway devicein a format of a call detail record (CDR).
 16. A method for transmittingwireless messages from a Wireless Access Internet Network architecturefor providing users a plurality of wireless protocols to access acommunications network, the method comprising: transmitting anauthentication message from a wireless client wherein the message istransmitted through a first radio link adaptation layer and a radiointerface, wherein the radio adaptation layer adapts the authenticationmessage to a plurality of wireless protocols; receiving theauthentication message at a wireless server in communication with thewireless client through a second radio link adaptation layer and a radioaccess point in communication with the radio interface wherein thewireless server includes: a charging module; a Home Location Register(HLR) signaling module; a Domain Naming System (DNS)/Dynamic HostConfiguration Protocol (DHCP) Remote Authentication Dial-in User Service(RADIUS) module; and transmitting the authentication message from thewireless server to a data network.
 17. The method of claim 16 furtherincluding transmitting from a second wireless client to the wirelessserver.
 18. The method of claim 16 further including: transmitting aplurality of messages from a wireless mobile device with a cellularprotocol; and receiving the plurality of messages at a base stationsystem (BSS) in communication with the wireless mobile device andconnected to the data network wherein the wireless server can transmitmessages from the wireless client to the wireless mobile device throughthe data network and the BSS.
 19. The method of claim 16 furtherincluding: transmitting a plurality of messages from a wireless mobiledevice with a wireless protocol; receiving the plurality of messages ata receiving system in communication with the wireless mobile device;transmitting the plurality of messages from the receiving system to aSGSN in communication with the receiving system and connected to thedata network wherein the wireless server can transmit messages from thewireless client to the wireless mobile device through the data network,the SGSN and the receiving system.
 20. The method of claim 16 furtherincluding transmitting billing information to a charge and billinggateway device in communication with the wireless server.
 21. The methodof claim 16 further including transmitting a User ID and Password to aRADIUS server connected to the wireless server and receiving anappropriate approve/deny message back from the RADIUS server.
 22. Themethod of claim 16 further including transmitting an authenticationinformation request message to a HLR connected to the wireless serverand receiving requested authentication data back from the HLR.
 23. Themethod of claim 16 further including transmitting the authenticationmessage to a AuC connected to the wireless server and receiving anappropriate approve/deny message back from the AuC.
 24. The method ofclaim 16 further comprising: transmitting information about a uniqueauthentication key from an identity module to the wireless client,wherein the authentication message from the wireless client includes theinformation about the unique authentication key.
 25. The method of claim24 further comprising: transmitting the authentication message from thewireless server to an AuC; and receiving from the AuC a messageindicating the authenticity/inauthenticity of the information about theauthentication key.